Skip to content

Conversation

siennathesane
Copy link

Objective

  • Export internalized methods for to allow for custom render worlds by exposing the few remaining internal pieces of RenderPlugin.

Solution

I am building a Monte Carlo simulation engine with Bevy and using ECS for simulation management and the render world to run pipelined compute shaders with render graphs. This exposes a few internal methods so I can build a custom render world that doesn't have camera, mesh, texture, or other plugins for pure headless environments (re: testing, server-side, etc.)

I assumed if I need it to, someone else might later!

Testing

  • Did you test these changes? If so, how?
    • No, they are just identifiers.
  • Are there any parts that need more testing?
    • No
  • How can other people (reviewers) test your changes? Is there anything specific they need to know?
    • 🤷🏼‍♀️
  • If relevant, what platforms did you test these changes on, and are there any important ones you can't test?
    • I can test on MacOS, but not any others.

Signed-off-by: Sienna Meridian Satterwhite <[email protected]>
Copy link
Contributor

Welcome, new contributor!

Please make sure you've read our contributing guide and we look forward to reviewing your pull request shortly ✨

Copy link
Member

@alice-i-cecile alice-i-cecile left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would prefer if we had docs on these newly public types, but I can live with it.

@alice-i-cecile alice-i-cecile added A-Rendering Drawing game state to the screen C-Usability A targeted quality-of-life change that makes Bevy easier to use X-Contentious There are nontrivial implications that should be thought through D-Straightforward Simple bug fixes and API improvements, docs, test and examples labels Sep 29, 2025
@alice-i-cecile alice-i-cecile added the S-Needs-Review Needs reviewer attention (from anyone!) to move forward label Sep 29, 2025
@siennathesane
Copy link
Author

@alice-i-cecile would you like me to add documentation to the change? I can also do it as a follow-on, too.

@alice-i-cecile
Copy link
Member

I'm always happy for more documentation :) Seperate PR is a bit cleaner (since then it won't get bogged down), but whatever is easiest for you. This is non-blocking.

@siennathesane
Copy link
Author

I will do it in a follow-on PR then!

Copy link
Member

@tychedelia tychedelia left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm fine with this as long as we either note that this behavior is not stable or hide these from rustdoc.

@siennathesane
Copy link
Author

I'm fine with this as long as we either note that this behavior is not stable or hide these from rustdoc.

Would you like me to mark the docs with #[unstable]?

@alice-i-cecile
Copy link
Member

Sure, that sounds nice.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Rendering Drawing game state to the screen C-Usability A targeted quality-of-life change that makes Bevy easier to use D-Straightforward Simple bug fixes and API improvements, docs, test and examples S-Needs-Review Needs reviewer attention (from anyone!) to move forward X-Contentious There are nontrivial implications that should be thought through
Projects
Status: No status
Development

Successfully merging this pull request may close these issues.

3 participants